![]() | Documentation Contents |
The JDBC-ODBC Bridge driver is recommended only for experimental use or when no other alternative is available.
The JDBC-ODBC Bridge driver is recommended for use in prototyping efforts and for cases where no other JDBC technology-based driver exists. If a commercial, all-Java JDBC driver is available, we recommend that it be used instead of the Bridge.
sun.jdbc.odbc
Java package and contains a native
library used to access ODBC. The Bridge is a joint development of
Merant and Java Software.
On Solaris, the JDBC 2.0 bridge must be used with an ODBC 3.x driver manager. The bridge supports both ODBC 2.x and ODBC 3.x drivers, but has been tested with only ODBC 3.x drivers.
On NT, the JDBC 2.0 bridge supports the ODBC 2.x and ODBC 3.x driver manager and drivers. The JDBC 2.0 bridge has been tested only with an ODBC 3.x driver manager and with both ODBC 2.x and 3.x drivers.
Merant recommends that the JDBC 2.0 bridge be used with version 3.5 or higher of Merant's DataDirect ODBC drivers.
sun.jdbc.odbc
. See your ODBC
driver vendor for information on installing and configuring ODBC.
No special configuration is required for the Bridge. See your
database vendor for client installation and configuration
information. On Solaris, some ODBC driver managers name their libs
libodbcinst.so
and libodbc.so
. The Bridge
expects these libraries to be named libodbcinst.so.1
and libodbc.so.1
, so symbolic links for these names
must be created.
odbc
subprotocol. See
below for URL examples. Before a connection can be established, the
bridge driver class, sun.jdbc.odbc.JdbcOdbcDriver
,
must either be added to the java.lang.System
property
named jdbc.drivers
, or it must be explicitly loaded
using the Java class loader. Explicit loading is done with the
following line of code:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");When loaded, the ODBC driver (like all good JDBC drivers) creates an instance of itself and registers this with the JDBC driver manager.
http:\\www.merant.com
. The MS SQL Server
driver has also been used successfully on NT. Many other ODBC
drivers will likely work.
odbc
subprotocol. URLs for this subprotocol are of the form:
jdbc:odbc:<data-source-name>[<attribute-name>=<attribute-value>]*
For example:
jdbc:odbc:sybase jdbc:odbc:mydb;UID=me;PWD=secret jdbc:odbc:ora123;Cachesize=300
DriverManager
tracing is enabled. The following line
of code enables tracing and sends it to standard out:
java.sql.DriverManager.setLogStream(java.lang.System.out);
The JDBC-ODBC Bridge driver in this release supports the following new features in the JDBC 2.0 API:
BigDecimal
methodsDate
, Time
, and
Timestamp
methodsThe current release of the Bridge supports multi-threaded ODBC
drivers and contains numerous bug fixes.
[Top] [Prev] [Next]
Copyright © 1993, 2011, Oracle and/or its affiliates. All rights reserved. Please send comments using this Feedback page. |
![]() Java Technology |